Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: replace all mentions and links of alequetzalli to quetzalliwrites #3393

Conversation

bandantonio
Copy link
Contributor

@bandantonio bandantonio commented Nov 13, 2024

Description

Personal rebranding for @quetzalliwrites 😀

Related issue(s)

Fixes #3389
Closes #3176

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features
    • Updated contributor name from "Alejandra Quetzalli" to "Quetzalli Writes" across various documentation and reports.
    • Introduced a new section in the mentorship document listing current cohort projects.
  • Bug Fixes
    • Corrected author links and profile images to reflect the new name.
  • Documentation
    • Enhanced clarity and consistency in reports and documentation regarding the updated author attribution.
    • Added links for "Quetzalli Writes" in various documents.
  • Chores
    • Updated various markdown files to maintain uniformity in author references.

Copy link

coderabbitai bot commented Nov 13, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes updates to various documentation files to replace all instances of the contributor's name "Alejandra Quetzalli" with "Quetzalli Writes." This change is reflected across multiple Markdown files, the .all-contributorsrc file, and the config/orbitData.json file, ensuring consistent attribution for contributions. The modifications also involve updating links and images associated with the contributor, while the overall structure and content of the documents remain intact.

Changes

File Path Change Summary
.all-contributorsrc Updated contributor entry from "Alejandra Quetzalli" to "Quetzalli Writes" with new login and profile.
README.md Replaced "Alejandra Quetzalli" with "Quetzalli Writes" in the contributors section.
assets/docs/fragments/contribution-notes.md Updated GitHub handle from "alequetzalli" to "quetzalliwrites."
config/orbitData.json Changed image entry from "ale.webp" to "que.webp" and updated the alt text.
markdown/blog/*.md Updated author name, photo, and LinkedIn link from "Alejandra Quetzalli" to "Quetzalli Writes" across multiple blog reports.
markdown/blog/conference-2022.md Added new volunteer entry for "Quetzalli Writes" in the volunteers section.
markdown/blog/google-season-of-docs-2022.md Updated author name and related links to reflect the new name.
markdown/blog/socketio-part1.md Updated reviewer acknowledgment from "alequetzalli" to "quetzalliwrites."
markdown/blog/socketio-part2.md Minor updates to author acknowledgments; no structural changes.

Assessment against linked issues

Objective Addressed Explanation
Replace all occurrences of "alequetzalli" throughout the docs (#3389)
Update GitHub handle link for "alequetzalli" (#3176)

Possibly related PRs

  • docs: replace duplicated content with reusable fragments #3269: The changes in this PR involve updating documentation to replace duplicated content with reusable fragments, which includes updates to contributor information that aligns with the changes made in the main PR regarding the contributor "Quetzalli Writes."
  • docs(concepts): improve writing style #3354: This PR focuses on improving the writing style in the Concepts section, which may indirectly relate to the overall documentation updates, including contributor information, as it aims to enhance clarity and consistency across the documentation.
  • docs(community): update latest tsc members list #3397: This PR updates the Ambassadors list, which may include references to contributors like "Quetzalli Writes," ensuring that the documentation reflects the most current information about contributors.

Suggested labels

ready-to-merge, autoapproved, autoupdate

Suggested reviewers

  • magicmatatjahu
  • devilkiller-ag
  • sambhavgupta0705
  • anshgoyalevil
  • quetzalliwrites
  • asyncapi-bot-eve
  • J0SAL
  • VaishnaviNandakumar

Poem

In the land of code where bunnies hop,
Quetzalli Writes now takes the top!
With every change, the docs align,
A name reborn, a tale divine.
Hopping through updates, clear and bright,
Our contributions shine with delight! 🐇✨


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cfca320 and c41ddf1.

📒 Files selected for processing (1)
  • README.md (1 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Nov 13, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit c41ddf1
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/674afb17f14ca50008c9b2b2
😎 Deploy Preview https://deploy-preview-3393--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Nov 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.77%. Comparing base (20e3649) to head (c41ddf1).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3393   +/-   ##
=======================================
  Coverage   67.77%   67.77%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          450      450           
  Misses        214      214           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Nov 13, 2024

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 33
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3393--asyncapi-website.netlify.app/

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (4)
markdown/blog/april-2023.md (1)

16-16: Consider updating the nickname reference for consistency

The paragraph uses "Ale" as a nickname while using "Quetzalli Writes" in formal references. For consistency with the rebranding effort, consider updating "Ale" to "Quetzalli" or removing the nickname entirely.

markdown/blog/2024-Q1-docs-report.md (1)

18-18: Add missing article "the"

Consider adding the article "the" before "AsyncAPI Initiative" for better grammar:

-collaborate with other areas in AsyncAPI Initiative.
+collaborate with other areas in the AsyncAPI Initiative.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

markdown/blog/google-season-of-docs-2022.md (1)

22-22: Consider using en dashes for date ranges

For better typography, consider replacing hyphens with en dashes in date ranges.

Apply these changes:

-31 Jan - 11 Feb 2022
+31 Jan – 11 Feb 2022
-14 Feb - 25 Feb 2022
+14 Feb – 25 Feb 2022
-28 Feb - 11 March 2022
+28 Feb – 11 March 2022

Also applies to: 59-59

🧰 Tools
🪛 LanguageTool

[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...

(DASH_RULE)

markdown/blog/release-notes-3.0.0.md (1)

362-362: Fix markdown linting issue: remove spaces inside link text.

The current format has spaces inside the link text which triggers the MD039 linting rule.

Apply this diff to fix the markdown linting issue:

-[Quetzalli Writes](https://github.com/quetzalliwrites)
+[QuetzalliWrites](https://github.com/quetzalliwrites)
🧰 Tools
🪛 Markdownlint

362-362: null
Spaces inside link text

(MD039, no-space-in-links)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6f15381 and 04a6bda.

📒 Files selected for processing (21)
  • .all-contributorsrc (1 hunks)
  • README.md (1 hunks)
  • assets/docs/fragments/contribution-notes.md (1 hunks)
  • config/orbitData.json (1 hunks)
  • markdown/blog/2022Q1-summary.md (3 hunks)
  • markdown/blog/2023-April-docs-report.md (3 hunks)
  • markdown/blog/2023-Q1-docs-report.md (2 hunks)
  • markdown/blog/2023-Q4-docs-report.md (2 hunks)
  • markdown/blog/2023-july-docs-report.md (1 hunks)
  • markdown/blog/2023-june-docs-report.md (1 hunks)
  • markdown/blog/2023-may-docs-report.md (1 hunks)
  • markdown/blog/2024-Q1-docs-report.md (1 hunks)
  • markdown/blog/2024-february-summary.md (1 hunks)
  • markdown/blog/april-2023.md (1 hunks)
  • markdown/blog/beyond-boundaries.md (1 hunks)
  • markdown/blog/changes-coming-docs.md (1 hunks)
  • markdown/blog/conference-2022.md (1 hunks)
  • markdown/blog/google-season-of-docs-2022.md (4 hunks)
  • markdown/blog/release-notes-3.0.0.md (1 hunks)
  • markdown/blog/socketio-part1.md (1 hunks)
  • markdown/blog/socketio-part2.md (1 hunks)
✅ Files skipped from review due to trivial changes (4)
  • README.md
  • assets/docs/fragments/contribution-notes.md
  • config/orbitData.json
  • markdown/blog/socketio-part1.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2022Q1-summary.md

[uncategorized] ~150-~150: Loose punctuation mark.
Context: ...oup of people to work on docs, checked. ✅ Our [new docs informa...

(UNLIKELY_OPENING_PUNCTUATION)

markdown/blog/2024-Q1-docs-report.md

[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

markdown/blog/google-season-of-docs-2022.md

[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...

(DASH_RULE)


[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ns here in [AsyncAPI Docs update (31 Jan - 11 Feb 2022)](https://gist.github.com/qu...

(DASH_RULE)


[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...4a3b56e2), [AsyncAPI Docs update (14 Feb - 25 Feb 2022)](https://gist.github.com/qu...

(DASH_RULE)


[typographical] ~59-~59: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...b477), and [AsyncAPI Docs update (28 Feb - 11 March 2022)](https://gist.github.com/...

(DASH_RULE)

🪛 Markdownlint
markdown/blog/google-season-of-docs-2022.md

96-96: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

markdown/blog/release-notes-3.0.0.md

362-362: null
Spaces inside link text

(MD039, no-space-in-links)

🔇 Additional comments (28)
markdown/blog/2023-may-docs-report.md (2)

Line range hint 16-17: Verify rebranding in imported fragments.

The file imports two fragments that might contain author references. Let's verify these have been updated as well.

#!/bin/bash
# Description: Check imported fragments for any remaining old name references

# Check the imported fragment files
rg -i "alequetzalli" "assets/docs/fragments/contribution-notes.md" "assets/docs/fragments/talk-to-me.md"

10-12: Verify the existence and consistency of the new avatar image.

The author information has been correctly updated to reflect the new branding. However, let's ensure the new avatar image exists and is properly referenced.

✅ Verification successful

Avatar image exists and branding is consistent

The new avatar image canela-quetzalli.webp exists in the correct location at public/img/avatars/, and the rebranding to "Quetzalli Writes" has been consistently applied across the codebase. Only one outdated reference was found in an issue title within dashboard.json, which is not part of the content files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new avatar image and check for any remaining old references

# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/

# Look for any remaining references to the old name
rg -i "alequetzalli" .

Length of output: 314


Script:

#!/bin/bash
# Let's verify the image path and check for any references to both old and new branding

# Check if the image exists in the correct location
fd "canela-quetzalli.webp" .

# Check for any references to the new branding
rg -i "quetzalli-writes|quetzalli writes" .

# Check the structure of public/img/avatars directory
fd . "public/img/avatars" || ls -la public/img/avatars 2>/dev/null || find . -path "*/img/avatars" -type d

Length of output: 10929

markdown/blog/2023-july-docs-report.md (1)

10-12: LGTM! Author information updated correctly.

The changes align with the PR objectives to update the author's information consistently.

Let's verify the referenced resources exist:

✅ Verification successful

Resources verified successfully

The verification confirms:

  • The new avatar image canela-quetzalli.webp exists at the correct location
  • No remaining references to the old name were found in markdown files
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the new avatar image exists and there are no remaining old references

# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/

# Verify no remaining references to old name
rg -i "alejandra|alequetzalli" --type md

Length of output: 130

markdown/blog/2024-february-summary.md (1)

16-16: LGTM! Verify the LinkedIn profile link.

The name update aligns with the rebranding request. The sentence structure and attribution are maintained correctly.

Let's verify the LinkedIn profile link is active and points to the correct profile:

✅ Verification successful

LinkedIn profile link format is correct and follows standard conventions

The LinkedIn profile URL follows the expected format https://www.linkedin.com/in/quetzalli-writes and matches LinkedIn's standard URL pattern for personal profiles.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the LinkedIn profile link format and accessibility
# Note: This only checks the URL format as actual HTTP requests to LinkedIn may be blocked

# Extract and verify the LinkedIn URL format
echo "Checking LinkedIn URL format..."
if rg -q 'https://www\.linkedin\.com/in/quetzalli-writes(/)?$' ; then
    echo "LinkedIn URL format is valid"
else
    echo "LinkedIn URL format may need review"
fi

Length of output: 201

markdown/blog/april-2023.md (1)

16-16: Verify the LinkedIn profile link

The LinkedIn profile link has been updated to reflect the rebranding. Let's verify it's working correctly.

markdown/blog/2024-Q1-docs-report.md (1)

18-18: LGTM!

The self-reference update is consistent with the rebranding effort.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~18-~18: You might be missing the article “the” here.
Context: ...ibutors collaborate with other areas in AsyncAPI Initiative. ## Overview During Q1 2024...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

markdown/blog/changes-coming-docs.md (2)

20-20: LGTM! Author introduction updates are consistent.

The personal introduction changes maintain consistency with the front matter updates while preserving the warm and engaging tone of the content.

Also applies to: 24-24, 26-26


10-12: Verify resource availability.

The author attribution changes look good and align with the rebranding effort.

Let's verify the resources exist:

✅ Verification successful

Resource verification completed successfully

The changes are consistent with the broader rebranding effort across the codebase:

  • The new avatar image canela-quetzalli.webp exists in the correct location
  • The new name "Quetzalli Writes" is consistently used across multiple blog posts and configuration files
  • No references to the old avatar name were found
  • The LinkedIn profile link format follows the standard pattern used in other files
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new avatar image

# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/

# Verify the old image is not referenced elsewhere
rg "canela-ale.webp"

Length of output: 108


Script:

#!/bin/bash
# Let's verify if there are any other references to the old or new author name
# across the codebase to ensure consistency

# Search for old name variations
rg -i "alejandra quetzalli"

# Search for new name
rg -i "quetzalli writes"

# Check for any other avatar references
rg -i "canela.*\.webp"

Length of output: 9291

markdown/blog/2023-Q4-docs-report.md (3)

21-21: LGTM! Author reference updated correctly

The self-reference update is consistent with the rebranding effort while maintaining the original context and tone of the document.


Line range hint 1-150: Verify no remaining instances of the old username

Let's ensure no references to the old username remain in the document:

✅ Verification successful

Since the search for the old username "alequetzalli" returned no results, and the document uses the new name "Quetzalli Writes" consistently, I can provide the final response:

No instances of old username found in the document

The document has been properly updated to use the new name "Quetzalli Writes" throughout, including the author attribution and content. No traces of the old username were found in any URLs or references.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for any remaining instances of the old username in the document

# Search for any instances of "alequetzalli" (case-insensitive)
rg -i "alequetzalli" markdown/blog/2023-Q4-docs-report.md

# Search for any URLs that might contain the old username
rg -i "https?://[^\s)]+alequetzalli[^\s)]+" markdown/blog/2023-Q4-docs-report.md

Length of output: 140


10-12: Verify the updated resources are accessible

The author information has been updated correctly. Let's verify the resources:

markdown/blog/2023-April-docs-report.md (3)

10-12: LGTM! Author details updated correctly.

The frontmatter changes accurately reflect the rebranding from "Alejandra Quetzalli" to "Quetzalli Writes", including the name, photo path, and LinkedIn profile link.


26-26: LGTM! Content updates maintain consistency.

All references to the author have been properly updated while preserving the original context and meaning of the content.

Also applies to: 29-29, 31-31, 34-34, 40-40, 58-58


11-11: Verify the new avatar image exists.

Please ensure that the new avatar image file /img/avatars/canela-quetzalli.webp has been added to the repository.

✅ Verification successful

Avatar image exists and no old references found

The new avatar image /img/avatars/canela-quetzalli.webp exists in the correct location and there are no remaining references to the old name in markdown files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new avatar image and check for any remaining old references

# Check if the new avatar image exists
fd "canela-quetzalli.webp" public/img/avatars/

# Check for any remaining references to the old name
rg -i "alejandra quetzalli|alequetzalli" --type md

Length of output: 140

markdown/blog/2023-june-docs-report.md (1)

10-12: LGTM! The author information has been updated correctly.

The changes align with the PR objectives to update references from "alequetzalli" to "quetzalliwrites".

Let's verify the new assets and links:

✅ Verification successful

The author information update is consistent and valid

The verification confirms:

  • The new avatar image exists at the correct path: public/img/avatars/canela-quetzalli.webp
  • The new LinkedIn profile URL linkedin.com/in/quetzalli-writes is used consistently across multiple blog posts
  • No lingering references to the old name variations or LinkedIn profile were found
  • The changes align with the broader rebranding effort
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new avatar image and LinkedIn profile

# Check if the new avatar image exists in the repository
fd "canela-quetzalli.webp" "public/img/avatars/"

# Check if this image is referenced in other files that might need updating
rg "canela-ale\.webp" --type md

# Verify the LinkedIn profile URL is consistently updated across all files
rg "linkedin\.com/in/alejandra-quetzalli" --type md

Length of output: 175


Script:

#!/bin/bash
# Let's do a broader search to find any remaining references to the old name/profile
# that might need updating

# Search for any mentions of the old name variations
rg -i "alejandra.?quetzalli|alequetzalli" --type md

# Search for any old LinkedIn profile patterns
rg "linkedin\.com/in/ale(jandra)?-?quetzalli" --type md

# Check for any other files referencing the old avatar image pattern
rg "canela-ale" --type md

# Let's also verify the new LinkedIn profile is used consistently
rg "linkedin\.com/in/quetzalli-writes" --type md

Length of output: 2914

markdown/blog/conference-2022.md (1)

152-156: LGTM! Verify GitHub profile links.

The profile entry for Quetzalli Writes follows the consistent structure and correctly implements the rebranding.

Let's verify the GitHub profile and avatar links:

✅ Verification successful

GitHub profile and avatar links verified successfully

Both the GitHub profile quetzalliwrites and the avatar URL are accessible and working correctly.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the GitHub profile exists and the avatar URL is accessible

# Check if the GitHub profile exists
gh api users/quetzalliwrites --jq '.login' || echo "GitHub profile not found"

# Check if the avatar URL is accessible
curl -s -I "https://avatars.githubusercontent.com/quetzalliwrites" | head -n 1 | grep "HTTP/[0-9.]* 200" || echo "Avatar URL not accessible"

Length of output: 175

markdown/blog/2023-Q1-docs-report.md (2)

92-92: LGTM! Author references updated consistently

The content references have been updated to use "Quetzalli" consistently, maintaining the original context and meaning of the text.

Also applies to: 94-94


10-12: Verify the new avatar image exists

The author information has been updated correctly, but we should verify that the new image file exists at the specified path.

✅ Verification successful

Avatar image path is valid

The referenced avatar image file canela-quetzalli.webp exists at the correct path /img/avatars/ in the public directory.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the new avatar image exists in the public directory
fd -t f "canela-quetzalli.webp" public/img/avatars/

Length of output: 92

markdown/blog/beyond-boundaries.md (1)

77-77: LGTM! Name and GitHub handle updated correctly.

The change correctly updates the mentor's name to "Quetzalli Writes" and the corresponding GitHub handle to "quetzalliwrites" in the mentorship projects table, aligning with the rebranding effort.

Let's verify there are no other occurrences of the old name in this file:

✅ Verification successful

No remaining occurrences of old name found - change is complete

The verification shows that there are no remaining instances of "alequetzalli" or "Alejandra Quetzalli" in the file, confirming that the rebranding has been properly implemented.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining instances of the old name/handle
# Note: Using case-insensitive search to catch any variations

echo "Checking for any remaining instances of 'alequetzalli' or 'Alejandra Quetzalli'..."
rg -i "alequetzalli|alejandra.?quetzalli" "markdown/blog/beyond-boundaries.md"

Length of output: 265

markdown/blog/google-season-of-docs-2022.md (3)

96-96: LGTM! Signature updated correctly

The signature has been updated to match the new branding while maintaining the same style.

🧰 Tools
🪛 Markdownlint

96-96: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


22-22: Verify Gist link accessibility

The Gist links have been updated to reflect the new username.

Let's verify the accessibility of the updated Gist links:

#!/bin/bash
# Description: Verify Gist links are accessible and no old references remain

# Extract and verify all Gist URLs
rg -o 'https://gist\.github\.com/[^/)]+' . | while read -r url; do
  echo "Checking $url..."
  curl -s -I "$url" | head -n 1
done

# Double-check for any remaining old Gist references
rg -i "gist\.github\.com/alequetzalli" .

Also applies to: 59-59

🧰 Tools
🪛 LanguageTool

[typographical] ~22-~22: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ber from my [Gist Docs update for 31 Jan - 11 Feb 2022](https://gist.github.com/que...

(DASH_RULE)


10-12: Verify new author assets and links

The author metadata changes align with the rebranding objectives.

Let's verify the new image path and LinkedIn profile URL:

✅ Verification successful

Author metadata changes verified successfully

The verification shows that:

  • The new image path public/img/avatars/canela-quetzalli.webp exists in the repository
  • The LinkedIn profile URL format is consistent with other blog posts
  • The author rebranding from "alequetzalli" to "quetzalliwrites" is consistently applied across the codebase, with only one remaining reference to the old handle in a historical bug report (dashboard.json)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new author image and profile links

# Check if the new image exists in the public directory
fd -t f "canela-quetzalli.webp" 

# Search for any remaining old references to ensure complete migration
rg -i "alequetzalli" .

Length of output: 2252


Script:

#!/bin/bash
# Let's try a different approach to verify the image and references

# Check for the image in public directory and any other common static asset directories
fd "canela-quetzalli.webp" -t f

# Look for any remaining references to the old username
rg -i "alequetzalli" --type md --type yaml --type json

# Check for any other instances of the new username to ensure consistency
rg -i "quetzalli-writes|quetzalliwrites" --type md --type yaml --type json

Length of output: 9702

markdown/blog/2022Q1-summary.md (4)

123-124: LGTM! Name and link updates are consistent

The changes correctly update the contributor's name and add appropriate link references while maintaining the original context about GSoD mentorship.

Also applies to: 126-126


150-150: LGTM! Name and link updates are consistent

The change correctly updates the contributor's name and adds the appropriate link reference while maintaining the original context about GSoD efforts.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~150-~150: Loose punctuation mark.
Context: ...oup of people to work on docs, checked. ✅ Our [new docs informa...

(UNLIKELY_OPENING_PUNCTUATION)


167-167: LGTM! Name and link updates are consistent

The change correctly updates the contributor's name and adds the appropriate link reference in the list of acknowledgments.


172-172: LGTM! Link references are properly defined

The changes correctly update the name reference and add well-structured link definitions at the bottom of the file. The spacing is maintained for proper markdown rendering.

Also applies to: 175-177

.all-contributorsrc (1)

64-67: LGTM! Contributor information updated correctly.

The changes accurately reflect the rebranding from "alequetzalli" to "quetzalliwrites" while maintaining the integrity of other contributor information.

Let's verify there are no remaining references to the old username in the codebase:

markdown/blog/release-notes-3.0.0.md (1)

362-362: LGTM! Name update aligns with rebranding.

The change correctly updates the contributor's name from "alequetzalli" to "Quetzalli Writes" while maintaining the proper link to their GitHub profile.

🧰 Tools
🪛 Markdownlint

362-362: null
Spaces inside link text

(MD039, no-space-in-links)

Comment on lines +10 to +12
- name: Quetzalli Writes
photo: /img/avatars/canela-quetzalli.webp
link: https://www.linkedin.com/in/quetzalli-writes/
Copy link

@coderabbitai coderabbitai bot Nov 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Image path needs to be updated

The avatar image exists but is located at /public/img/avatars/canela-quetzalli.webp while the markdown references it at /img/avatars/canela-quetzalli.webp. Update the path to include the public prefix.

🔗 Analysis chain

Verify the existence of the new avatar image

The author information has been updated correctly. However, let's verify that the new avatar image exists in the repository.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the new avatar image exists
fd -t f "canela-quetzalli.webp" img/avatars/

Length of output: 144


Script:

#!/bin/bash
# Let's first check if the image directory exists and its location
fd -t d "avatars"

# Then search for the image file across the repository
fd -t f "canela-quetzalli.webp"

# Also check for any similar image names
fd -t f "quetzalli"

Length of output: 171

Copy link
Contributor Author

@bandantonio bandantonio Nov 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not relevant, as public is the default location for different static assets. The static-site generator uses this location and appends the public prefix automatically

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bandantonio, understood. Thank you for the clarification.


✏️ Learnings added
Learnt from: bandantonio
PR: asyncapi/website#3393
File: markdown/blog/2024-Q1-docs-report.md:10-12
Timestamp: 2024-11-13T20:34:17.145Z
Learning: In the markdown files for the AsyncAPI website, avatar image paths should be referenced without the `public` prefix (e.g., use `/img/avatars/...` instead of `/public/img/avatars/...`).

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

markdown/blog/socketio-part2.md Show resolved Hide resolved
@akshatnema akshatnema merged commit 20ab113 into asyncapi:master Nov 30, 2024
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants